Hi everyone, I hope that I can get some help on this. I have been seeing email getting stuck in the local delivery queue for sometime now. I turned on the MsExchange Store Driver logs to Maximum and started getting this: Event ID: 327 Category : Exchange Store DriverSource : MSExchangeTransportType : WarningDescription: The following call : EcLocallyDeliverMsg to the store failed. Error code : -1017 (Message-ID <47BB56E4.7060106@unpri.org>). MDB : faed628a-dfac-411b-8538-25b41a05cfa8. FID : 1-33. MID : 78-2E006E006500. File : . I have seen all the various articles on this problem but dealing with different error codes. I am just not sure if any of those solutions apply to my case. I am running Windows 2003 Server with Exchange Server SP2. If there is anyone who have encountered this particular problem before I would appreciate your help. Thanks very much. --Dtek from New York City.

i think you needrun isinteg to fix the problem.Please review following MSKB or yor references. http://support.microsoft.com/kb/328671 http://support.microsoft.com/kb/924206 Regards Billy

Hey Billy, thanks for your very helpful response. I suspected that the Antivirus may have scanned the c:\Exchsrvr directory causing database corruption. So you are saying that I would have to do an offline database defragmentation and then run isinteg -s ServerName -fix -test alltests after to make sure that all errors are fixed and down to 0? I know that this is usually a last resort. Does it make sense to make a backup before I do this? I know I will surely have to make a backup after I do this since after running eseutil, would render any backups that I did before useless. Once again thanks.

Billy..another bit of what I think is very important information. I am journaling emails to an outside source. The emails that comes in from the outside are going to the store just fine. Users are indeed receiving their emails fine. The problem is occuring when a copy of the emails are to go to the journal mailbox. Those are the ones that are getting stuck in the local queue. And it is only just a few that are getting stuck..not all of them. Perhaps instead of running eseutil /d and isinteg -s ServerName -fix -test alltests on the mailbox database files, I can run those on the journal database? I found out what mails are getting stuck by using the email tracking center. Once again..thanks for your response. If anyone else reads this and have any other ideas I will be gladfor your help. --DtekNYC